Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad558dcf8efaf5344a1700ae31b866096a12e631d0f99e4eba5f4401096130fd

Tx prefix hash: d503c41e97796b130b8ab635410de8b75c243cfdc7627af21500fb2b811ddd29
Tx public key: 2f852291d4d89b3a4012d234962d1a584e91be69ee080da8bc0ec4a3ccf1b66f
Timestamp: 1763101148 Timestamp [UCT]: 2025-11-14 06:19:08 Age [y:d:h:m:s]: 00:076:20:54:44
Block: 1411758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54868 RingCT/type: yes/0
Extra: 012f852291d4d89b3a4012d234962d1a584e91be69ee080da8bc0ec4a3ccf1b66f0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ab197262262a8710ac4ec74429826622fc891e1479a3bedca2df7ab072d0b5e 0.600000000000 1900221 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": 1411768, "vin": [ { "gen": { "height": 1411758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ab197262262a8710ac4ec74429826622fc891e1479a3bedca2df7ab072d0b5e" } } ], "extra": [ 1, 47, 133, 34, 145, 212, 216, 155, 58, 64, 18, 210, 52, 150, 45, 26, 88, 78, 145, 190, 105, 238, 8, 13, 168, 188, 14, 196, 163, 204, 241, 182, 111, 2, 17, 0, 0, 0, 4, 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