Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: aca6855826d589c1eba3b2148e5183395d86b94d0c1217ecb8799319b9f5f7c0

Tx prefix hash: 2265b1e14dd5a011872c821640b38f313d848cfa87aee8adb97032f5b29d43f3
Tx public key: 68aea250a3f54441e8318fca9a35233572914a8a98416e166b874a095873732c
Timestamp: 1711588281 Timestamp [UCT]: 2024-03-28 01:11:21 Age [y:d:h:m:s]: 00:276:17:21:43
Block: 987833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198063 RingCT/type: yes/0
Extra: 0168aea250a3f54441e8318fca9a35233572914a8a98416e166b874a095873732c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3f4d55db327c1b832c9a7bc0bd7e7f31e05e9da455761a25fc06e3b8be97c26 0.600000000000 1448092 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 987843, "vin": [ { "gen": { "height": 987833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3f4d55db327c1b832c9a7bc0bd7e7f31e05e9da455761a25fc06e3b8be97c26" } } ], "extra": [ 1, 104, 174, 162, 80, 163, 245, 68, 65, 232, 49, 143, 202, 154, 53, 35, 53, 114, 145, 74, 138, 152, 65, 110, 22, 107, 135, 74, 9, 88, 115, 115, 44, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8