Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca3e16298d183c3df73d08c02d4cb849bd645f1a793bd1b4cc9783f5bb7eb7a7

Tx prefix hash: 44f8578352e33933dd05afbb296d3ac9549bf528c6745e737037a18ea464f4c1
Tx public key: 4c5754af928fd36d4e4599fa04ae3b59479fe27262309e7cb7d82b9591381e9c
Timestamp: 1764398472 Timestamp [UCT]: 2025-11-29 06:41:12 Age [y:d:h:m:s]: 00:035:06:12:30
Block: 1422517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25242 RingCT/type: yes/0
Extra: 014c5754af928fd36d4e4599fa04ae3b59479fe27262309e7cb7d82b9591381e9c02110000000334af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5b40a996e1adc009a46265d331f63d136d5ff89e950bca8c19ede06e0e0c15b 0.600000000000 1911084 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": 1422527, "vin": [ { "gen": { "height": 1422517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5b40a996e1adc009a46265d331f63d136d5ff89e950bca8c19ede06e0e0c15b" } } ], "extra": [ 1, 76, 87, 84, 175, 146, 143, 211, 109, 78, 69, 153, 250, 4, 174, 59, 89, 71, 159, 226, 114, 98, 48, 158, 124, 183, 216, 43, 149, 145, 56, 30, 156, 2, 17, 0, 0, 0, 3, 52, 175, 49, 204, 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