Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7c17e4b289895ca38b790f70a4e2d0b1e3a309f71800034a9a3339514241af0

Tx prefix hash: cc9c17f01ed41e09a4c01bb61d121f9f85388260c0d3c9d0e61657fcee8398d0
Tx public key: 8913d17acc6f318e662e3faceb8a6913a48a526601c97aeff48573d49c8fadff
Timestamp: 1723834721 Timestamp [UCT]: 2024-08-16 18:58:41 Age [y:d:h:m:s]: 00:143:16:04:19
Block: 1089348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102769 RingCT/type: yes/0
Extra: 018913d17acc6f318e662e3faceb8a6913a48a526601c97aeff48573d49c8fadff02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1363b4e646efa92341cf2222bd0d05f1aa3882e2bad7e352a8465727d22a2f7b 0.600000000000 1563967 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": 1089358, "vin": [ { "gen": { "height": 1089348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1363b4e646efa92341cf2222bd0d05f1aa3882e2bad7e352a8465727d22a2f7b" } } ], "extra": [ 1, 137, 19, 209, 122, 204, 111, 49, 142, 102, 46, 63, 172, 235, 138, 105, 19, 164, 138, 82, 102, 1, 201, 122, 239, 244, 133, 115, 212, 156, 143, 173, 255, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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