Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb5d49f9b024feaa36d8ef720884a6cfb00cb75482b63736276a14284ddfd1b1

Tx prefix hash: 68b0e30a39f6ad8d2818e85b75dce6e0ae64fda034f6442341204c9bb7c1b649
Tx public key: 9ce32ee965d9df480e3a1589edcbd8892aaaddc992b8dcfe6b22a9832120e101
Timestamp: 1716397255 Timestamp [UCT]: 2024-05-22 17:00:55 Age [y:d:h:m:s]: 00:315:06:44:00
Block: 1027677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225341 RingCT/type: yes/0
Extra: 019ce32ee965d9df480e3a1589edcbd8892aaaddc992b8dcfe6b22a9832120e1010211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d639c6e3fd10421a98c111c938b25e8ae528eb82a06dbf36761a475d38fedc4 0.600000000000 1495432 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": 1027687, "vin": [ { "gen": { "height": 1027677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d639c6e3fd10421a98c111c938b25e8ae528eb82a06dbf36761a475d38fedc4" } } ], "extra": [ 1, 156, 227, 46, 233, 101, 217, 223, 72, 14, 58, 21, 137, 237, 203, 216, 137, 42, 170, 221, 201, 146, 184, 220, 254, 107, 34, 169, 131, 33, 32, 225, 1, 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