Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9decd6a4a60f4cc48f021ef9df1479e17e204d0dc0a8b97f3cd906e3e268f7a2

Tx prefix hash: 14ed204eb48149e0f264ac3e97c1ea3551d8de45a9ddba3b153961eabd4b5790
Tx public key: afe9edcfebef8f7577e1de8e7f7a0efc50a3f73957008b4b5280105f9e295fc0
Timestamp: 1615138518 Timestamp [UCT]: 2021-03-07 17:35:18 Age [y:d:h:m:s]: 03:257:11:31:14
Block: 213520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 943368 RingCT/type: yes/0
Extra: 01afe9edcfebef8f7577e1de8e7f7a0efc50a3f73957008b4b5280105f9e295fc00211000000133a645b90000000000000000000

1 output(s) for total of 120.370539647000 dcy

stealth address amount amount idx
00: a0f9fe2c1d5d20979200836850b801e289854859ae00992dc3ae1ef7f0a1e52c 120.370539647000 435792 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": 213530, "vin": [ { "gen": { "height": 213520 } } ], "vout": [ { "amount": 120370539647, "target": { "key": "a0f9fe2c1d5d20979200836850b801e289854859ae00992dc3ae1ef7f0a1e52c" } } ], "extra": [ 1, 175, 233, 237, 207, 235, 239, 143, 117, 119, 225, 222, 142, 127, 122, 14, 252, 80, 163, 247, 57, 87, 0, 139, 75, 82, 128, 16, 95, 158, 41, 95, 192, 2, 17, 0, 0, 0, 19, 58, 100, 91, 144, 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