Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0813068745c9dba32fce803ef9a14a53fd3b35b50dd0f6a4ee2f8ce1e9c653df

Tx prefix hash: 5d3fbbed3bad2661f2a8bf78dd477a5f343612456d50155d8b804b9b7e9b6f06
Tx public key: c6b58b9952f4d18e7e61ee38469fdeb13948b1209e90910e0156418877cecb11
Timestamp: 1721225404 Timestamp [UCT]: 2024-07-17 14:10:04 Age [y:d:h:m:s]: 00:219:21:33:43
Block: 1067724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157025 RingCT/type: yes/0
Extra: 01c6b58b9952f4d18e7e61ee38469fdeb13948b1209e90910e0156418877cecb11021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80c84eaed38a9332d4a8df18b222102a0226c0269eee1cb89e26d2042a6485da 0.600000000000 1538619 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": 1067734, "vin": [ { "gen": { "height": 1067724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80c84eaed38a9332d4a8df18b222102a0226c0269eee1cb89e26d2042a6485da" } } ], "extra": [ 1, 198, 181, 139, 153, 82, 244, 209, 142, 126, 97, 238, 56, 70, 159, 222, 177, 57, 72, 177, 32, 158, 144, 145, 14, 1, 86, 65, 136, 119, 206, 203, 17, 2, 17, 0, 0, 0, 2, 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