Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f77bf7c4517413baad3e2a9d6da31c737e988faf9edbdcf8e511b785cccb64d

Tx prefix hash: cb01eb398e7b10e4290d7cad59b50d1c40d6b5a4b615aab3ccf922fb7a7a9ff9
Tx public key: b6429f5e7405c4a33da4769bf103cfda788b203d0ee2648ec5e2982ea5ab318f
Timestamp: 1744339523 Timestamp [UCT]: 2025-04-11 02:45:23 Age [y:d:h:m:s]: 00:272:02:16:28
Block: 1258843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192267 RingCT/type: yes/0
Extra: 01b6429f5e7405c4a33da4769bf103cfda788b203d0ee2648ec5e2982ea5ab318f0211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30dfe5509a42c68981ccb9a66f8505bcd98138a8f306f3a043d346de94234261 0.600000000000 1745980 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": 1258853, "vin": [ { "gen": { "height": 1258843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30dfe5509a42c68981ccb9a66f8505bcd98138a8f306f3a043d346de94234261" } } ], "extra": [ 1, 182, 66, 159, 94, 116, 5, 196, 163, 61, 164, 118, 155, 241, 3, 207, 218, 120, 139, 32, 61, 14, 226, 100, 142, 197, 226, 152, 46, 165, 171, 49, 143, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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