Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a555da207933624e70e567e3f8336275a9342c9ba8d46180883c9fd46c89eb2d

Tx prefix hash: d697001049705ff5002a3ab6f4389ad0a844f1a7e17e174b7e020dc1e41f874a
Tx public key: 37e1086b4926c5c7af58b9c1a40b9222028a4e034fad4cf93d619ab3b1333544
Timestamp: 1709115806 Timestamp [UCT]: 2024-02-28 10:23:26 Age [y:d:h:m:s]: 01:015:14:24:52
Block: 967333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272156 RingCT/type: yes/0
Extra: 0137e1086b4926c5c7af58b9c1a40b9222028a4e034fad4cf93d619ab3b13335440211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 838be9f53aa510890286301aa826747cbda2d45f212ad0383ea84746aacef51d 0.600000000000 1427110 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": 967343, "vin": [ { "gen": { "height": 967333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "838be9f53aa510890286301aa826747cbda2d45f212ad0383ea84746aacef51d" } } ], "extra": [ 1, 55, 225, 8, 107, 73, 38, 197, 199, 175, 88, 185, 193, 164, 11, 146, 34, 2, 138, 78, 3, 79, 173, 76, 249, 61, 97, 154, 179, 177, 51, 53, 68, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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