Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a581d99c591dacc833f4fda63e2e72c50092d3f3695629f197dfbeb36fe0d85e

Tx prefix hash: 8f40c52d698951024697013c5c502a3a39cc578a07153ab4b2bbae334d96ff06
Tx public key: 67e76b0568a85809d726b1222b209f1779abca39f3af3bf62a8e4d33e6063a14
Timestamp: 1711701597 Timestamp [UCT]: 2024-03-29 08:39:57 Age [y:d:h:m:s]: 01:077:22:41:58
Block: 988770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316619 RingCT/type: yes/0
Extra: 0167e76b0568a85809d726b1222b209f1779abca39f3af3bf62a8e4d33e6063a140211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95c920a7b8653c0d7d55f82a261762a6a5e6d9a83da2ef025daca6043373c146 0.600000000000 1449055 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": 988780, "vin": [ { "gen": { "height": 988770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95c920a7b8653c0d7d55f82a261762a6a5e6d9a83da2ef025daca6043373c146" } } ], "extra": [ 1, 103, 231, 107, 5, 104, 168, 88, 9, 215, 38, 177, 34, 43, 32, 159, 23, 121, 171, 202, 57, 243, 175, 59, 246, 42, 142, 77, 51, 230, 6, 58, 20, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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