Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1923d95ae829cb6d64169c89acddcc8d38e99944a56f4096d4319541e8cc3217

Tx prefix hash: 71023e2e3af4b6250735ed09270ac36dda866fb8a5ab9451ad1154dfd2f5df88
Tx public key: b745191b65646c94a363544ed7e173e5f98b653d78b87c1ddbe5a634a0786e0e
Timestamp: 1731718842 Timestamp [UCT]: 2024-11-16 01:00:42 Age [y:d:h:m:s]: 00:195:06:19:09
Block: 1154625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139417 RingCT/type: yes/0
Extra: 01b745191b65646c94a363544ed7e173e5f98b653d78b87c1ddbe5a634a0786e0e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7a2b5e45f15f0d3e2454e980e1a6a1f9b9f1f3100bca0ed59ad1bfda8103d78 0.600000000000 1640238 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": 1154635, "vin": [ { "gen": { "height": 1154625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7a2b5e45f15f0d3e2454e980e1a6a1f9b9f1f3100bca0ed59ad1bfda8103d78" } } ], "extra": [ 1, 183, 69, 25, 27, 101, 100, 108, 148, 163, 99, 84, 78, 215, 225, 115, 229, 249, 139, 101, 61, 120, 184, 124, 29, 219, 229, 166, 52, 160, 120, 110, 14, 2, 17, 0, 0, 0, 5, 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