Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b56ea1fd25420dbe735875a340805fd179d40d696ac64de65802338574be418

Tx prefix hash: ed613a6a0e5c39f44fc5c324b96a25275e874160d91b9517a8fe23caa3644bd5
Tx public key: ad3c604ad687d509379ff976837de1a003df367e4ebbc3a1cea724b9cfd1c6e1
Timestamp: 1700692684 Timestamp [UCT]: 2023-11-22 22:38:04 Age [y:d:h:m:s]: 01:095:07:54:32
Block: 897484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329262 RingCT/type: yes/0
Extra: 01ad3c604ad687d509379ff976837de1a003df367e4ebbc3a1cea724b9cfd1c6e102110000000775e3f0e9000000000000000000

1 output(s) for total of 0.652023024000 dcy

stealth address amount amount idx
00: f8d863066ee0e919be45e29ae3cae50fdb35b33d36f79483f4739390845b6a24 0.652023024000 1353865 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": 897494, "vin": [ { "gen": { "height": 897484 } } ], "vout": [ { "amount": 652023024, "target": { "key": "f8d863066ee0e919be45e29ae3cae50fdb35b33d36f79483f4739390845b6a24" } } ], "extra": [ 1, 173, 60, 96, 74, 214, 135, 213, 9, 55, 159, 249, 118, 131, 125, 225, 160, 3, 223, 54, 126, 78, 187, 195, 161, 206, 167, 36, 185, 207, 209, 198, 225, 2, 17, 0, 0, 0, 7, 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