Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834092d86b426050045ed66368518e43e74a1f025222774a95cd71d5950f8960

Tx prefix hash: b7cccbc715d7de440e9ecf67c1abb72e60bfab9e8b1c021840883a898a8f64bd
Tx public key: c4a1933edeaeafa45ca46f26e3e0f731506fdafb8ed2e546cb89a0fd91ca0bcc
Timestamp: 1737349844 Timestamp [UCT]: 2025-01-20 05:10:44 Age [y:d:h:m:s]: 00:149:07:20:28
Block: 1201199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106458 RingCT/type: yes/0
Extra: 01c4a1933edeaeafa45ca46f26e3e0f731506fdafb8ed2e546cb89a0fd91ca0bcc0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 504cb46544e35ddfb5a67bef01f043dc3d39da335a1a02d7d2e1c5174114963e 0.600000000000 1687848 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": 1201209, "vin": [ { "gen": { "height": 1201199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "504cb46544e35ddfb5a67bef01f043dc3d39da335a1a02d7d2e1c5174114963e" } } ], "extra": [ 1, 196, 161, 147, 62, 222, 174, 175, 164, 92, 164, 111, 38, 227, 224, 247, 49, 80, 111, 218, 251, 142, 210, 229, 70, 203, 137, 160, 253, 145, 202, 11, 204, 2, 17, 0, 0, 0, 4, 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