Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c73d48e67787cdaa0d2e3ef6bc23628255b0008d41769d403cc2b6cbc2545a1

Tx prefix hash: d579bbc477cb6c549cca5daf12f22ddff546d0a89b25c53964f63ddffcb2fe5a
Tx public key: 52b0f5642641e9dbaa94b2cf9c2fd0e023772f2931ec00223e2cde8c21c0ff74
Timestamp: 1719413980 Timestamp [UCT]: 2024-06-26 14:59:40 Age [y:d:h:m:s]: 00:321:21:22:20
Block: 1052690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230053 RingCT/type: yes/0
Extra: 0152b0f5642641e9dbaa94b2cf9c2fd0e023772f2931ec00223e2cde8c21c0ff740211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8805b9ee06b7427cd7c6c5ffbe831973947adb5fb5180d24688b9d1188f8a50a 0.600000000000 1523021 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": 1052700, "vin": [ { "gen": { "height": 1052690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8805b9ee06b7427cd7c6c5ffbe831973947adb5fb5180d24688b9d1188f8a50a" } } ], "extra": [ 1, 82, 176, 245, 100, 38, 65, 233, 219, 170, 148, 178, 207, 156, 47, 208, 224, 35, 119, 47, 41, 49, 236, 0, 34, 62, 44, 222, 140, 33, 192, 255, 116, 2, 17, 0, 0, 0, 4, 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