Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0992c192e65486401e0ac074b7235c7f44a0b7efe23a0bc1ca0102e59a2b84a

Tx prefix hash: 29e953e3fdf978588f835fb282fe0f9c790ab396c8a58e674744c00c692b781d
Tx public key: e5694ecb43ef2ece60a53525fa694b9c199c7c8246a4bc8ee4553a628715140b
Timestamp: 1725593621 Timestamp [UCT]: 2024-09-06 03:33:41 Age [y:d:h:m:s]: 00:139:03:15:28
Block: 1103928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99473 RingCT/type: yes/0
Extra: 01e5694ecb43ef2ece60a53525fa694b9c199c7c8246a4bc8ee4553a628715140b021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91404bf96d6889014ed9b46b938f301a00746b25ebf325caa4ed40e76cad163f 0.600000000000 1580947 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": 1103938, "vin": [ { "gen": { "height": 1103928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91404bf96d6889014ed9b46b938f301a00746b25ebf325caa4ed40e76cad163f" } } ], "extra": [ 1, 229, 105, 78, 203, 67, 239, 46, 206, 96, 165, 53, 37, 250, 105, 75, 156, 25, 156, 124, 130, 70, 164, 188, 142, 228, 85, 58, 98, 135, 21, 20, 11, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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