Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353166b5f7d24124de95d7d0b6ee3a6877452cb8d5d54ec99992ae928c182c47

Tx prefix hash: c7364dae8a1aad957d087281b1d7d63fd7e3a5756c0920360dcd39ee29d018cd
Tx public key: 37a2e5d7c1dfdf505599eebc5c01038113267365b0d0976462b794a08f94620b
Timestamp: 1721299216 Timestamp [UCT]: 2024-07-18 10:40:16 Age [y:d:h:m:s]: 00:265:09:11:25
Block: 1068345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189572 RingCT/type: yes/0
Extra: 0137a2e5d7c1dfdf505599eebc5c01038113267365b0d0976462b794a08f94620b021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b87dc873ccf2c338e33894be72d499c3af60436ebdadda4fb26e70caedd84cb7 0.600000000000 1539422 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": 1068355, "vin": [ { "gen": { "height": 1068345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b87dc873ccf2c338e33894be72d499c3af60436ebdadda4fb26e70caedd84cb7" } } ], "extra": [ 1, 55, 162, 229, 215, 193, 223, 223, 80, 85, 153, 238, 188, 92, 1, 3, 129, 19, 38, 115, 101, 176, 208, 151, 100, 98, 183, 148, 160, 143, 148, 98, 11, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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