Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a7b8e0e28762873c1b5d8af38e95f94cd4d6a13f98d5235b7d22b434444c0a2

Tx prefix hash: f96bc88b051bfe56b123ae1bb8f63b6bd923310d799035c5535472a2c5861d6a
Tx public key: 4ad1d668252c6dfbe1ac9f61889deb4f1655f294f23610eb2d23bc9dca68fe07
Timestamp: 1736971164 Timestamp [UCT]: 2025-01-15 19:59:24 Age [y:d:h:m:s]: 00:154:20:17:31
Block: 1198103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110371 RingCT/type: yes/0
Extra: 014ad1d668252c6dfbe1ac9f61889deb4f1655f294f23610eb2d23bc9dca68fe070211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7777337d39da0688c81899611ae33ca2f24f55163e40f5de20b00af0640db13b 0.600000000000 1684722 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": 1198113, "vin": [ { "gen": { "height": 1198103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7777337d39da0688c81899611ae33ca2f24f55163e40f5de20b00af0640db13b" } } ], "extra": [ 1, 74, 209, 214, 104, 37, 44, 109, 251, 225, 172, 159, 97, 136, 157, 235, 79, 22, 85, 242, 148, 242, 54, 16, 235, 45, 35, 188, 157, 202, 104, 254, 7, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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