Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f007ff4e466c867e9eb98dac869635bcfe5b91d0301e60618b47f630cb87ea6c

Tx prefix hash: 02302945b28c7f5588e5541916b1819898e97b6a7a16da591f913e4a1bd2909e
Tx public key: 8951e068d8daea2e5ff4d867d460c5e1f0943b34a8aaf11fda3ba8a3cc1cf135
Timestamp: 1720027489 Timestamp [UCT]: 2024-07-03 17:24:49 Age [y:d:h:m:s]: 00:287:12:58:41
Block: 1057786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205453 RingCT/type: yes/0
Extra: 018951e068d8daea2e5ff4d867d460c5e1f0943b34a8aaf11fda3ba8a3cc1cf1350211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c326964c0633d4e0fd9cf7edb217b60e28d20429e766af451016cc5925928802 0.600000000000 1528227 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": 1057796, "vin": [ { "gen": { "height": 1057786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c326964c0633d4e0fd9cf7edb217b60e28d20429e766af451016cc5925928802" } } ], "extra": [ 1, 137, 81, 224, 104, 216, 218, 234, 46, 95, 244, 216, 103, 212, 96, 197, 225, 240, 148, 59, 52, 168, 170, 241, 31, 218, 59, 168, 163, 204, 28, 241, 53, 2, 17, 0, 0, 0, 5, 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