Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc85a7e4ef943eb480ab621dc4816e5169dc80747949e59ff2a1be4dfc06a4ac

Tx prefix hash: 287080c06196456829d97fc5e73042d9dfe0d7427c3fb2e7f5aee022408cee32
Tx public key: 68cbe741c08b2d66f65520f9752121837db5a31c2e440d136e3347f0e7789a41
Timestamp: 1721087473 Timestamp [UCT]: 2024-07-15 23:51:13 Age [y:d:h:m:s]: 00:259:11:44:05
Block: 1066580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185363 RingCT/type: yes/0
Extra: 0168cbe741c08b2d66f65520f9752121837db5a31c2e440d136e3347f0e7789a4102110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea0f0da2a7e4b049f743392a28d6b764b15befa918b29b0ad1a35588b50cefd 0.600000000000 1537247 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": 1066590, "vin": [ { "gen": { "height": 1066580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea0f0da2a7e4b049f743392a28d6b764b15befa918b29b0ad1a35588b50cefd" } } ], "extra": [ 1, 104, 203, 231, 65, 192, 139, 45, 102, 246, 85, 32, 249, 117, 33, 33, 131, 125, 181, 163, 28, 46, 68, 13, 19, 110, 51, 71, 240, 231, 120, 154, 65, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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