Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c67544e0f16d029b97b5fb09c2d5698ad7703a219e80d21af969fd44a82c054

Tx prefix hash: f87bf03f4d0089a3037329314bf06e094f46596b96d47b231613f6d3fee1d9a8
Tx public key: 8bc6ad6c7c1e409f5e1c6054f1cd1ccfa3fd8f0f7598c8b266ff5365e409164d
Timestamp: 1734297761 Timestamp [UCT]: 2024-12-15 21:22:41 Age [y:d:h:m:s]: 00:106:07:37:13
Block: 1176004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75751 RingCT/type: yes/0
Extra: 018bc6ad6c7c1e409f5e1c6054f1cd1ccfa3fd8f0f7598c8b266ff5365e409164d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ccaab56d0a3ffc5c0edc0d670697f9119967d4b74bb1b686a45990a6f5a8efe 0.600000000000 1662331 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": 1176014, "vin": [ { "gen": { "height": 1176004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ccaab56d0a3ffc5c0edc0d670697f9119967d4b74bb1b686a45990a6f5a8efe" } } ], "extra": [ 1, 139, 198, 173, 108, 124, 30, 64, 159, 94, 28, 96, 84, 241, 205, 28, 207, 163, 253, 143, 15, 117, 152, 200, 178, 102, 255, 83, 101, 228, 9, 22, 77, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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