Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d3e948ec1fbc8fb08a97a334e65c9e89c892bfc212d435ef5b0c710d2550a9c

Tx prefix hash: a62335a2a3507df52b0fa5cbdd8f919c19947dc18ae4e0fdc6267691d4719054
Tx public key: 8a3d29822c40a09908e4e7041b5dec44f65f6fd586f5ba5f5be909fd8d9e4bcd
Timestamp: 1748024162 Timestamp [UCT]: 2025-05-23 18:16:02 Age [y:d:h:m:s]: 00:230:11:36:50
Block: 1289354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162493 RingCT/type: yes/0
Extra: 018a3d29822c40a09908e4e7041b5dec44f65f6fd586f5ba5f5be909fd8d9e4bcd0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 127c45618370c62224275fdf148d93068d780e865d6df5ccac60d3176e611e3b 0.600000000000 1776823 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": 1289364, "vin": [ { "gen": { "height": 1289354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "127c45618370c62224275fdf148d93068d780e865d6df5ccac60d3176e611e3b" } } ], "extra": [ 1, 138, 61, 41, 130, 44, 64, 160, 153, 8, 228, 231, 4, 27, 93, 236, 68, 246, 95, 111, 213, 134, 245, 186, 95, 91, 233, 9, 253, 141, 158, 75, 205, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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