Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf87b70f3ca9297b05d43fcb72860a3e4ae270347306e99ab5d476a8f88ad281

Tx prefix hash: 3cacac668de1c192eb92073c5c5643997e64bf172fc21668ded8d458e51902e5
Tx public key: fd4f9c685dfcbdc9457b56472918cbf29ff247e8147008a5daca8c681bee966c
Timestamp: 1750985777 Timestamp [UCT]: 2025-06-27 00:56:17 Age [y:d:h:m:s]: 00:194:09:50:36
Block: 1313519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137039 RingCT/type: yes/0
Extra: 01fd4f9c685dfcbdc9457b56472918cbf29ff247e8147008a5daca8c681bee966c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e77d9aa550b7410c6dc07f4da2ce29b5da91c4f33fdbf4677b1aa1a06e71903b 0.600000000000 1801160 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": 1313529, "vin": [ { "gen": { "height": 1313519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e77d9aa550b7410c6dc07f4da2ce29b5da91c4f33fdbf4677b1aa1a06e71903b" } } ], "extra": [ 1, 253, 79, 156, 104, 93, 252, 189, 201, 69, 123, 86, 71, 41, 24, 203, 242, 159, 242, 71, 232, 20, 112, 8, 165, 218, 202, 140, 104, 27, 238, 150, 108, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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