Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7324575523186991f814da22cc93e5d32ce64c8e61a0f11268ae863c7420dcb

Tx prefix hash: 78763856111381658bf72732c3d3630454fca76329839b01e60a3a9ce7259d93
Tx public key: 3a909311fd9ce7f79a4c65a90d3a10d712d89fd9d69f2b35fe5509ec18e7ff59
Timestamp: 1712982697 Timestamp [UCT]: 2024-04-13 04:31:37 Age [y:d:h:m:s]: 00:318:07:58:23
Block: 999350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227584 RingCT/type: yes/0
Extra: 013a909311fd9ce7f79a4c65a90d3a10d712d89fd9d69f2b35fe5509ec18e7ff590211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64234889633973fbbbf8914bafa64c06950f812c5be2ce5eb2ed70e3c56944b0 0.600000000000 1459828 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": 999360, "vin": [ { "gen": { "height": 999350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64234889633973fbbbf8914bafa64c06950f812c5be2ce5eb2ed70e3c56944b0" } } ], "extra": [ 1, 58, 144, 147, 17, 253, 156, 231, 247, 154, 76, 101, 169, 13, 58, 16, 215, 18, 216, 159, 217, 214, 159, 43, 53, 254, 85, 9, 236, 24, 231, 255, 89, 2, 17, 0, 0, 0, 3, 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