Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e903e24538ed37335ff54df1fb5321b9da9c8d23eed4b4be481ac02cab8a4924

Tx prefix hash: 12949654c1912d3c3f0faba0d1424afdf10e0af46545256853a1ae13c1696b00
Tx public key: 33ec0cd9f9c8cc693f7e0bc4a3514f52ebd1a96f76d6d857fd2778f67dcfa5d2
Timestamp: 1653337599 Timestamp [UCT]: 2022-05-23 20:26:39 Age [y:d:h:m:s]: 03:161:03:28:34
Block: 507394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 894162 RingCT/type: yes/0
Extra: 0133ec0cd9f9c8cc693f7e0bc4a3514f52ebd1a96f76d6d857fd2778f67dcfa5d202110000000ac9067537000000000000000000

1 output(s) for total of 12.787723682000 dcy

stealth address amount amount idx
00: bb16eea8a919c9ece870a2ff66c61abd6bb3d098d5953dc161ddf731d8b5b70e 12.787723682000 933143 of 0

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": 507404, "vin": [ { "gen": { "height": 507394 } } ], "vout": [ { "amount": 12787723682, "target": { "key": "bb16eea8a919c9ece870a2ff66c61abd6bb3d098d5953dc161ddf731d8b5b70e" } } ], "extra": [ 1, 51, 236, 12, 217, 249, 200, 204, 105, 63, 126, 11, 196, 163, 81, 79, 82, 235, 209, 169, 111, 118, 214, 216, 87, 253, 39, 120, 246, 125, 207, 165, 210, 2, 17, 0, 0, 0, 10, 201, 6, 117, 55, 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