Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ef806477190874d2c467a995ed7d4e138c2a989b844f1f58c1ba3050c3c70dd

Tx prefix hash: b2b6cbcd2d436672038e221d9b04240db62f2a2308811de67068b99dc12e8dca
Tx public key: f26f3fa051f670fca45c6e11c3896c2f20040b9b0c0a5803ef06bc6824880a77
Timestamp: 1708108201 Timestamp [UCT]: 2024-02-16 18:30:01 Age [y:d:h:m:s]: 00:331:08:20:34
Block: 958965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237200 RingCT/type: yes/0
Extra: 01f26f3fa051f670fca45c6e11c3896c2f20040b9b0c0a5803ef06bc6824880a7702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f667957a7470a113a3d9da3ec7f42476b9fbf24dc06324f6ca84afc46656f17 0.600000000000 1418458 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": 958975, "vin": [ { "gen": { "height": 958965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f667957a7470a113a3d9da3ec7f42476b9fbf24dc06324f6ca84afc46656f17" } } ], "extra": [ 1, 242, 111, 63, 160, 81, 246, 112, 252, 164, 92, 110, 17, 195, 137, 108, 47, 32, 4, 11, 155, 12, 10, 88, 3, 239, 6, 188, 104, 36, 136, 10, 119, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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