Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9708a322861e35e4f8d9c8556537c13d1cda60bbd877d92354d2139da3a5177c

Tx prefix hash: 93afc484d0782413706ead9e60274ed00954396a20db90aea6021a52408e6a0b
Tx public key: c12aff8268afac50ccbd511c590c1f5c01f833e4ad7fbb56421ee2c17a8279a6
Timestamp: 1721123115 Timestamp [UCT]: 2024-07-16 09:45:15 Age [y:d:h:m:s]: 00:131:00:53:09
Block: 1066883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93744 RingCT/type: yes/0
Extra: 01c12aff8268afac50ccbd511c590c1f5c01f833e4ad7fbb56421ee2c17a8279a602110000001d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4ef7e7c29501b73886244aa66394245939a4d53d3e88d27a8939f263a3ad1f 0.600000000000 1537558 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": 1066893, "vin": [ { "gen": { "height": 1066883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4ef7e7c29501b73886244aa66394245939a4d53d3e88d27a8939f263a3ad1f" } } ], "extra": [ 1, 193, 42, 255, 130, 104, 175, 172, 80, 204, 189, 81, 28, 89, 12, 31, 92, 1, 248, 51, 228, 173, 127, 187, 86, 66, 30, 226, 193, 122, 130, 121, 166, 2, 17, 0, 0, 0, 29, 145, 225, 60, 4, 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