Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5807cafa76732017375f80b51ba76285dd82ff3d9feab0da0f43ffc0ab5f734

Tx prefix hash: 50a8a353fa868dd1af4b01bfc5a993fe97d71bc309e900a76b5478488b83f4b3
Tx public key: b72e77d4b599064ad362d6ee2f86c6a7e99c14267a100c5f60bbfd1756d3ae43
Timestamp: 1761203179 Timestamp [UCT]: 2025-10-23 07:06:19 Age [y:d:h:m:s]: 00:098:21:15:04
Block: 1396042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70610 RingCT/type: yes/0
Extra: 01b72e77d4b599064ad362d6ee2f86c6a7e99c14267a100c5f60bbfd1756d3ae43021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b73c252208e2700bcd06812c5a1f16028f22639bf2bb1ae58bf2e4359f68e933 0.600000000000 1884327 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": 1396052, "vin": [ { "gen": { "height": 1396042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b73c252208e2700bcd06812c5a1f16028f22639bf2bb1ae58bf2e4359f68e933" } } ], "extra": [ 1, 183, 46, 119, 212, 181, 153, 6, 74, 211, 98, 214, 238, 47, 134, 198, 167, 233, 156, 20, 38, 122, 16, 12, 95, 96, 187, 253, 23, 86, 211, 174, 67, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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