Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db6b33329d2f7e6a75bb3566e93cea7f326670de716fc490e14a89ec2f780d6a

Tx prefix hash: a695e7a79f8e77a9d8e9976b48060f678052f3bc77be47373523fd80aa1c3412
Tx public key: 1457bc1e5c6f0e3f76cd509d1234f38dabcd31a3be036581d9a1261094123cf9
Timestamp: 1707686181 Timestamp [UCT]: 2024-02-11 21:16:21 Age [y:d:h:m:s]: 01:015:09:54:34
Block: 955461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272028 RingCT/type: yes/0
Extra: 011457bc1e5c6f0e3f76cd509d1234f38dabcd31a3be036581d9a1261094123cf90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b931f7c16ffa40537db9280cf7351ce9b44877f6dc5713d72d6c9c291e2aadc 0.600000000000 1414749 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": 955471, "vin": [ { "gen": { "height": 955461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b931f7c16ffa40537db9280cf7351ce9b44877f6dc5713d72d6c9c291e2aadc" } } ], "extra": [ 1, 20, 87, 188, 30, 92, 111, 14, 63, 118, 205, 80, 157, 18, 52, 243, 141, 171, 205, 49, 163, 190, 3, 101, 129, 217, 161, 38, 16, 148, 18, 60, 249, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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