Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 428e6b8016637d5f97356e250b3c4fcd1875b5c9a34b7794021a1a48c35a330e

Tx prefix hash: b05f1747753bb64c8dbb115099b90624b7db515f9f58ae2279731f9bf0827518
Tx public key: f2fca1b72758f68db880811b56e73cdf58339e0ad1ceb5f4c8977032a2f680d5
Timestamp: 1582507974 Timestamp [UCT]: 2020-02-24 01:32:54 Age [y:d:h:m:s]: 04:266:10:48:48
Block: 71078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083160 RingCT/type: yes/0
Extra: 01f2fca1b72758f68db880811b56e73cdf58339e0ad1ceb5f4c8977032a2f680d502110000000112c4732d000000000000000000

1 output(s) for total of 356.869415553000 dcy

stealth address amount amount idx
00: e7cb7c066e2451de41b9869caac287020b346c2d393c6f83bb1110df20c7fa3c 356.869415553000 131376 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": 71088, "vin": [ { "gen": { "height": 71078 } } ], "vout": [ { "amount": 356869415553, "target": { "key": "e7cb7c066e2451de41b9869caac287020b346c2d393c6f83bb1110df20c7fa3c" } } ], "extra": [ 1, 242, 252, 161, 183, 39, 88, 246, 141, 184, 128, 129, 27, 86, 231, 60, 223, 88, 51, 158, 10, 209, 206, 181, 244, 200, 151, 112, 50, 162, 246, 128, 213, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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