Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63a5a1ad87d91275a55a16b81ef3fb41d081dd2cd2fed0dd110d53b38d4285ac

Tx prefix hash: b0f9b50eae06d58e2debc546b9a30fbaf02e6fa45ee1e87062281235a531ead2
Tx public key: 382c987e9f2959d5127035788c2afc67a5aa74102e05453c99d46d43e3664e50
Timestamp: 1724496052 Timestamp [UCT]: 2024-08-24 10:40:52 Age [y:d:h:m:s]: 00:225:17:40:35
Block: 1094842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161174 RingCT/type: yes/0
Extra: 01382c987e9f2959d5127035788c2afc67a5aa74102e05453c99d46d43e3664e50021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3a7b39f9a6d9d9870f6dc36778266025a5b2e6e2423edd8681ec276482504f1 0.600000000000 1569963 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": 1094852, "vin": [ { "gen": { "height": 1094842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3a7b39f9a6d9d9870f6dc36778266025a5b2e6e2423edd8681ec276482504f1" } } ], "extra": [ 1, 56, 44, 152, 126, 159, 41, 89, 213, 18, 112, 53, 120, 140, 42, 252, 103, 165, 170, 116, 16, 46, 5, 69, 60, 153, 212, 109, 67, 227, 102, 78, 80, 2, 17, 0, 0, 0, 7, 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