Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b1d7b1f10fd81fa67fabdb74fbdd3695ebd88a404e91c66958025c091ad6e73

Tx prefix hash: 8066ded62f3ef903d784f1070654a7613cebb774deeb5e93cfe2bc4e5a2600b2
Tx public key: 54060e0c0aa24098e7b4f457847b88fef1c91aef634df4d5c58adc92ade35e28
Timestamp: 1707465351 Timestamp [UCT]: 2024-02-09 07:55:51 Age [y:d:h:m:s]: 01:060:10:33:16
Block: 953630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304245 RingCT/type: yes/0
Extra: 0154060e0c0aa24098e7b4f457847b88fef1c91aef634df4d5c58adc92ade35e28021100000001ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7744faf8cd8bfaf625c81941d9ff9b134dc6317a76fd56a8997159abba84b86a 0.600000000000 1412864 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": 953640, "vin": [ { "gen": { "height": 953630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7744faf8cd8bfaf625c81941d9ff9b134dc6317a76fd56a8997159abba84b86a" } } ], "extra": [ 1, 84, 6, 14, 12, 10, 162, 64, 152, 231, 180, 244, 87, 132, 123, 136, 254, 241, 201, 26, 239, 99, 77, 244, 213, 197, 138, 220, 146, 173, 227, 94, 40, 2, 17, 0, 0, 0, 1, 236, 87, 178, 52, 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