Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0ba12c8300d43c4115642aa09928d100e3b937957edbc66681adbcb4cdf5117

Tx prefix hash: 637e1e4019627ac661ca267db04e519cabc3f0c3567a5a2108607743f514b1a8
Tx public key: 19a65012b5a10225f16d05588dcade23b5fd723c2b74ef55d3966da4f7617ab4
Timestamp: 1724665580 Timestamp [UCT]: 2024-08-26 09:46:20 Age [y:d:h:m:s]: 00:090:06:17:03
Block: 1096228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64568 RingCT/type: yes/0
Extra: 0119a65012b5a10225f16d05588dcade23b5fd723c2b74ef55d3966da4f7617ab4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a5e6fc04d60c4ce2677cd26b1c2b2b8bff2928a870fd743e5d4affc596bdfb6 0.600000000000 1571415 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": 1096238, "vin": [ { "gen": { "height": 1096228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a5e6fc04d60c4ce2677cd26b1c2b2b8bff2928a870fd743e5d4affc596bdfb6" } } ], "extra": [ 1, 25, 166, 80, 18, 181, 161, 2, 37, 241, 109, 5, 88, 141, 202, 222, 35, 181, 253, 114, 60, 43, 116, 239, 85, 211, 150, 109, 164, 247, 97, 122, 180, 2, 17, 0, 0, 0, 5, 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