Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f98d5733873c351a17652b9261e6bf4c88bded86f49a1e1c2e0834f8f915dd80

Tx prefix hash: 4c948238b7fde6cb46ebc11c43d36f2110a019fdc31312f8d6a78a12b2b7c76f
Tx public key: de78d117b306c028e064a081894cafa3d998ede70ccd88f87b07ab6bce65133c
Timestamp: 1705696211 Timestamp [UCT]: 2024-01-19 20:30:11 Age [y:d:h:m:s]: 01:319:01:24:35
Block: 938944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486886 RingCT/type: yes/0
Extra: 01de78d117b306c028e064a081894cafa3d998ede70ccd88f87b07ab6bce65133c0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f3486fa0c5f60a68235d0b7a9ce56e5548794567b4d0bb7390468d56328a5bd 0.600000000000 1397028 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": 938954, "vin": [ { "gen": { "height": 938944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f3486fa0c5f60a68235d0b7a9ce56e5548794567b4d0bb7390468d56328a5bd" } } ], "extra": [ 1, 222, 120, 209, 23, 179, 6, 192, 40, 224, 100, 160, 129, 137, 76, 175, 163, 217, 152, 237, 231, 12, 205, 136, 248, 123, 7, 171, 107, 206, 101, 19, 60, 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