Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5c09c93bef9f5ea984bf5e4ee9f19247e79e96da599a9fb94c21ffca2557496

Tx prefix hash: 714da67d127ac1cbf345809ff84a1761460f4ab40d197174886941ec92b27ed1
Tx public key: f387d2f923e2abdd339b0a29d53ad159c9e6596bb0ccf585e026e25a4ab0fa77
Timestamp: 1724166632 Timestamp [UCT]: 2024-08-20 15:10:32 Age [y:d:h:m:s]: 00:302:02:51:30
Block: 1092107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215705 RingCT/type: yes/0
Extra: 01f387d2f923e2abdd339b0a29d53ad159c9e6596bb0ccf585e026e25a4ab0fa77021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ada0acc1487d02a863e28eec1c8baa6ffc6657277c2144595a5cab6241ce430c 0.600000000000 1566788 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": 1092117, "vin": [ { "gen": { "height": 1092107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ada0acc1487d02a863e28eec1c8baa6ffc6657277c2144595a5cab6241ce430c" } } ], "extra": [ 1, 243, 135, 210, 249, 35, 226, 171, 221, 51, 155, 10, 41, 213, 58, 209, 89, 201, 230, 89, 107, 176, 204, 245, 133, 224, 38, 226, 90, 74, 176, 250, 119, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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