Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c63ac14e56785537d3c84983f9ae3751017f03bfd8fc98baa31188508c6a5ff

Tx prefix hash: 90ed43e517857048244a3e174f0ded60f6b65111dc8609179fc3c2679302a681
Tx public key: 8f4768e31f6e10f6dbe14d258d15c653e8b1d2bb31366d41cb4795fc1017f999
Timestamp: 1727292162 Timestamp [UCT]: 2024-09-25 19:22:42 Age [y:d:h:m:s]: 00:197:06:42:51
Block: 1118013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140804 RingCT/type: yes/0
Extra: 018f4768e31f6e10f6dbe14d258d15c653e8b1d2bb31366d41cb4795fc1017f999021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74448d4bf603f099ad8d40147ed12586e2af2ea8a837862cacc3d3f6599e6faa 0.600000000000 1599058 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": 1118023, "vin": [ { "gen": { "height": 1118013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74448d4bf603f099ad8d40147ed12586e2af2ea8a837862cacc3d3f6599e6faa" } } ], "extra": [ 1, 143, 71, 104, 227, 31, 110, 16, 246, 219, 225, 77, 37, 141, 21, 198, 83, 232, 177, 210, 187, 49, 54, 109, 65, 203, 71, 149, 252, 16, 23, 249, 153, 2, 17, 0, 0, 0, 2, 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