Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f58cdbf411ae9631925516df3c091c2d76317b6edd4aa01a32a4eb39c8899ffc

Tx prefix hash: 670a9a3629417540b6f33501929836b5a788fcd50a314dffac9fe8715f2c6479
Tx public key: 4000c3dc87cddd7215bf67a3f690075a10950f20be98b741b5ebbe3436eb6984
Timestamp: 1663754714 Timestamp [UCT]: 2022-09-21 10:05:14 Age [y:d:h:m:s]: 02:180:12:13:55
Block: 592571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 650427 RingCT/type: yes/0
Extra: 014000c3dc87cddd7215bf67a3f690075a10950f20be98b741b5ebbe3436eb698402110000000233af99f4000000000000000000

1 output(s) for total of 6.676769135000 dcy

stealth address amount amount idx
00: 2b0aa46a5a6d90066c1ba0b3847dcbb723814b0b0e970e66e177b9294311d9fd 6.676769135000 1027250 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": 592581, "vin": [ { "gen": { "height": 592571 } } ], "vout": [ { "amount": 6676769135, "target": { "key": "2b0aa46a5a6d90066c1ba0b3847dcbb723814b0b0e970e66e177b9294311d9fd" } } ], "extra": [ 1, 64, 0, 195, 220, 135, 205, 221, 114, 21, 191, 103, 163, 246, 144, 7, 90, 16, 149, 15, 32, 190, 152, 183, 65, 181, 235, 190, 52, 54, 235, 105, 132, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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