Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a8d2a2ef3a7d682b8e56d1a3234bf9c2d99b2b158178059480008009c7e33d

Tx prefix hash: 9b75a5b358e64f4d52abec627fa026bef44010bba7d6d2c321fb05edb88d19b7
Tx public key: f0eb912d4c339f0c107efd3fc665713855d232353027c32ed4acf65d7f6f3254
Timestamp: 1750380417 Timestamp [UCT]: 2025-06-20 00:46:57 Age [y:d:h:m:s]: 00:153:21:03:21
Block: 1308715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107797 RingCT/type: yes/0
Extra: 01f0eb912d4c339f0c107efd3fc665713855d232353027c32ed4acf65d7f6f3254021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6362706919c912ac0bf9b1d9e7f220677687e58b115f14025172e0044983f42 0.600000000000 1796330 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": 1308725, "vin": [ { "gen": { "height": 1308715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6362706919c912ac0bf9b1d9e7f220677687e58b115f14025172e0044983f42" } } ], "extra": [ 1, 240, 235, 145, 45, 76, 51, 159, 12, 16, 126, 253, 63, 198, 101, 113, 56, 85, 210, 50, 53, 48, 39, 195, 46, 212, 172, 246, 93, 127, 111, 50, 84, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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