Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc0f65fdff571f0f5dc62adddfd88ecd4881889c10491be87f3c1e4a174915e8

Tx prefix hash: 40060d5ab9181ce6f121c7375b622a0426ce694e664492a50e04f0eeb8a04bae
Tx public key: df242649695d5d9ea35263fd2507a10daa80fd8aff68824d3ddf945e3cc78d53
Timestamp: 1684968238 Timestamp [UCT]: 2023-05-24 22:43:58 Age [y:d:h:m:s]: 01:335:03:57:34
Block: 767379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500754 RingCT/type: yes/0
Extra: 01df242649695d5d9ea35263fd2507a10daa80fd8aff68824d3ddf945e3cc78d5302110000000575e3f0e9000000000000000000

1 output(s) for total of 1.759361145000 dcy

stealth address amount amount idx
00: e628f83621717ae865b0022668e1d81aac9949ef9e63dd9d4b03067c8104c90d 1.759361145000 1216500 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": 767389, "vin": [ { "gen": { "height": 767379 } } ], "vout": [ { "amount": 1759361145, "target": { "key": "e628f83621717ae865b0022668e1d81aac9949ef9e63dd9d4b03067c8104c90d" } } ], "extra": [ 1, 223, 36, 38, 73, 105, 93, 93, 158, 163, 82, 99, 253, 37, 7, 161, 13, 170, 128, 253, 138, 255, 104, 130, 77, 61, 223, 148, 94, 60, 199, 141, 83, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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