Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7618f59d01a964b9af2391546fcb5a33a4b81e7989e47e03241ea2bf109f8f74

Tx prefix hash: 626179f67550d2ed4f254ffedaa02951e7f366da692864f04062cd09eaf2c7a1
Tx public key: 1dd26d566c8f9229694a300b1da43502f8ec2cf731e63b381fc63e7713e3b2c1
Timestamp: 1706808854 Timestamp [UCT]: 2024-02-01 17:34:14 Age [y:d:h:m:s]: 01:277:11:33:28
Block: 948180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457091 RingCT/type: yes/0
Extra: 011dd26d566c8f9229694a300b1da43502f8ec2cf731e63b381fc63e7713e3b2c10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5936a650a7aabb3b7bb027e34cfd55ada77aa9692d4faae3e9a1c0389afb00ee 0.600000000000 1406552 of 15

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": 948190, "vin": [ { "gen": { "height": 948180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5936a650a7aabb3b7bb027e34cfd55ada77aa9692d4faae3e9a1c0389afb00ee" } } ], "extra": [ 1, 29, 210, 109, 86, 108, 143, 146, 41, 105, 74, 48, 11, 29, 164, 53, 2, 248, 236, 44, 247, 49, 230, 59, 56, 31, 198, 62, 119, 19, 227, 178, 193, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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