Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4a4cd4e64046bd3d5e9c6b7d7e6a0044ccb7f45339e07f6fffad5c28c50e95b

Tx prefix hash: 916cfce32818ecdb5be1a9c6237013b5cb3de60d22fbfae1e55f9d26d716912f
Tx public key: 83b990a1f089b9965f98e529e33f189613e7f8c7abca0f73ac768fc53f9871ec
Timestamp: 1696354976 Timestamp [UCT]: 2023-10-03 17:42:56 Age [y:d:h:m:s]: 01:202:02:48:06
Block: 861727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405513 RingCT/type: yes/0
Extra: 0183b990a1f089b9965f98e529e33f189613e7f8c7abca0f73ac768fc53f9871ec021100000008faf35c9c000000000000000000

1 output(s) for total of 0.856526430000 dcy

stealth address amount amount idx
00: b381db766b4e047086fef3f4b9fd65fcd8e645518030f5afe47fc7b229e164c7 0.856526430000 1316093 of 0

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": 861737, "vin": [ { "gen": { "height": 861727 } } ], "vout": [ { "amount": 856526430, "target": { "key": "b381db766b4e047086fef3f4b9fd65fcd8e645518030f5afe47fc7b229e164c7" } } ], "extra": [ 1, 131, 185, 144, 161, 240, 137, 185, 150, 95, 152, 229, 41, 227, 63, 24, 150, 19, 231, 248, 199, 171, 202, 15, 115, 172, 118, 143, 197, 63, 152, 113, 236, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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