Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b448d2de36adf57a184f122a8a73b0d9d7b8cf675dedb7afc204c584ee06128

Tx prefix hash: 336801b6efac855749fb563e3592ae4f207fc3c95004c5dcf4476e5562657215
Tx public key: 5dcefc3768f8bac1e416edec020d4cb9b76d1c60670477d6de3ac7bbf3e57c2a
Timestamp: 1751893932 Timestamp [UCT]: 2025-07-07 13:12:12 Age [y:d:h:m:s]: 00:129:06:38:18
Block: 1320621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90817 RingCT/type: yes/0
Extra: 015dcefc3768f8bac1e416edec020d4cb9b76d1c60670477d6de3ac7bbf3e57c2a021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dba19c5e6a733a4afd72bbfa0d3f5e40fbb468bedad02a2534f45010f9a7169a 0.600000000000 1808320 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": 1320631, "vin": [ { "gen": { "height": 1320621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dba19c5e6a733a4afd72bbfa0d3f5e40fbb468bedad02a2534f45010f9a7169a" } } ], "extra": [ 1, 93, 206, 252, 55, 104, 248, 186, 193, 228, 22, 237, 236, 2, 13, 76, 185, 183, 109, 28, 96, 103, 4, 119, 214, 222, 58, 199, 187, 243, 229, 124, 42, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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