Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3654dcabd4896d0a1486c744324485b3c3b64e690b3bb817f7078a4382ffa3c

Tx prefix hash: 8aeb4eafac67ae72a91c09892a5647e2727f7499c42ec4b3c8324ad2fde08067
Tx public key: 19b00d4fd06819f4aebb93f7b3f0ec94f3339781e8b39d6b689779f6440296b4
Timestamp: 1732136311 Timestamp [UCT]: 2024-11-20 20:58:31 Age [y:d:h:m:s]: 00:115:23:25:45
Block: 1158072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82726 RingCT/type: yes/0
Extra: 0119b00d4fd06819f4aebb93f7b3f0ec94f3339781e8b39d6b689779f6440296b4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9625a6ff1935457a34cc51e19fc99f7ca4258fa5199314e6406dcf945284e02b 0.600000000000 1643701 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": 1158082, "vin": [ { "gen": { "height": 1158072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9625a6ff1935457a34cc51e19fc99f7ca4258fa5199314e6406dcf945284e02b" } } ], "extra": [ 1, 25, 176, 13, 79, 208, 104, 25, 244, 174, 187, 147, 247, 179, 240, 236, 148, 243, 51, 151, 129, 232, 179, 157, 107, 104, 151, 121, 246, 68, 2, 150, 180, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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