Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f22c206c575ea643a3776d83f2b046abfa877ea8b424a6e1858ca9a2a5c9d9fd

Tx prefix hash: 62f73b77507b6824b891f86a1d39c2dbfffdd518e0cea0fe9035bc9ee10500e0
Tx public key: d0f87e6f80b099b37a1ea6086996f0d0cb7b480d9c471c88217d640248e5ba85
Timestamp: 1754444044 Timestamp [UCT]: 2025-08-06 01:34:04 Age [y:d:h:m:s]: 00:017:18:01:32
Block: 1341156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11747 RingCT/type: yes/0
Extra: 01d0f87e6f80b099b37a1ea6086996f0d0cb7b480d9c471c88217d640248e5ba850211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1d6f6efefc562feb925060f65857c3484eaf2ddc6bf6f6a2e4ec62657c9e3ba 0.600000000000 1828979 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": 1341166, "vin": [ { "gen": { "height": 1341156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1d6f6efefc562feb925060f65857c3484eaf2ddc6bf6f6a2e4ec62657c9e3ba" } } ], "extra": [ 1, 208, 248, 126, 111, 128, 176, 153, 179, 122, 30, 166, 8, 105, 150, 240, 208, 203, 123, 72, 13, 156, 71, 28, 136, 33, 125, 100, 2, 72, 229, 186, 133, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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