Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa18be7cf815cbbdf43a72cf174ff92660149abbc11ddb41707b7a2ee1ef82d

Tx prefix hash: ad00e4ab6aaa9a8a04cf520332211237c5d8de298b137000b5de8d0d85419af1
Tx public key: 9dc45a4f79e58634f26e1244e5d46fb8833ee342fdd7f710e4a133c76b7de78a
Timestamp: 1711845942 Timestamp [UCT]: 2024-03-31 00:45:42 Age [y:d:h:m:s]: 01:074:09:40:10
Block: 989976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314111 RingCT/type: yes/0
Extra: 019dc45a4f79e58634f26e1244e5d46fb8833ee342fdd7f710e4a133c76b7de78a02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13632a157fb1cd4fb565debb68a82910b9d2a4ca1665de8471bd847d233b8d5b 0.600000000000 1450294 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": 989986, "vin": [ { "gen": { "height": 989976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13632a157fb1cd4fb565debb68a82910b9d2a4ca1665de8471bd847d233b8d5b" } } ], "extra": [ 1, 157, 196, 90, 79, 121, 229, 134, 52, 242, 110, 18, 68, 229, 212, 111, 184, 131, 62, 227, 66, 253, 215, 247, 16, 228, 161, 51, 199, 107, 125, 231, 138, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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