Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85a754e22b2d245d6dd82691b42c9a0ba29ad440022d4928a610aca40ad677b9

Tx prefix hash: cc0dd48af41179a691416ab2f8c5ec88e778b5c0d7c6d78337a8c6d5bf472174
Tx public key: cfbc0e09536c5911cb743cae256825ebd50d7e2cc0bb1fea23f320c2cab83b3c
Timestamp: 1750377188 Timestamp [UCT]: 2025-06-19 23:53:08 Age [y:d:h:m:s]: 00:154:04:23:45
Block: 1308685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108012 RingCT/type: yes/0
Extra: 01cfbc0e09536c5911cb743cae256825ebd50d7e2cc0bb1fea23f320c2cab83b3c0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfa859ab82bc42ed6a02a719c457fc4987572afe3299d2b57f65a94de75e0a70 0.600000000000 1796300 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": 1308695, "vin": [ { "gen": { "height": 1308685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfa859ab82bc42ed6a02a719c457fc4987572afe3299d2b57f65a94de75e0a70" } } ], "extra": [ 1, 207, 188, 14, 9, 83, 108, 89, 17, 203, 116, 60, 174, 37, 104, 37, 235, 213, 13, 126, 44, 192, 187, 31, 234, 35, 243, 32, 194, 202, 184, 59, 60, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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