Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78a2598010f3d1c23cc9f9f52df59d4b09fd235d365aee76d4c71244e26e1368

Tx prefix hash: e5f54631881cdfb40cc43daf16afcabfb842c44248ba7f33af57e35c4a48c7a7
Tx public key: 5b16d9284e586da8a2630f358756714da7f55455b260310404af5b68aae46d89
Timestamp: 1742526932 Timestamp [UCT]: 2025-03-21 03:15:32 Age [y:d:h:m:s]: 00:245:20:07:25
Block: 1243855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173418 RingCT/type: yes/0
Extra: 015b16d9284e586da8a2630f358756714da7f55455b260310404af5b68aae46d89021100000001bfa77623000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd6d26930895289a2abd3e5b30a8d45b82ac7cb9cad093ceae79a4714df98d7d 0.600000000000 1730846 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": 1243865, "vin": [ { "gen": { "height": 1243855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd6d26930895289a2abd3e5b30a8d45b82ac7cb9cad093ceae79a4714df98d7d" } } ], "extra": [ 1, 91, 22, 217, 40, 78, 88, 109, 168, 162, 99, 15, 53, 135, 86, 113, 77, 167, 245, 84, 85, 178, 96, 49, 4, 4, 175, 91, 104, 170, 228, 109, 137, 2, 17, 0, 0, 0, 1, 191, 167, 118, 35, 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