Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fad80561f080389688935569b7932df1d1b4569fb0bb9d490645e710541dadc2

Tx prefix hash: c9a92124e3bc3b79d5b37bfae8e61dd3768321b0a6517e3da13e1b7f819dfc68
Tx public key: a986be02ee4daa9f13be2f88c1c291146d96437dc4919c9fecc4c21534f0b9a8
Timestamp: 1716457947 Timestamp [UCT]: 2024-05-23 09:52:27 Age [y:d:h:m:s]: 00:318:23:05:32
Block: 1028197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227959 RingCT/type: yes/0
Extra: 01a986be02ee4daa9f13be2f88c1c291146d96437dc4919c9fecc4c21534f0b9a802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf54b5238ea1828b258dbae490576116ec559abb2b440eeffe4cc0629f80d8a4 0.600000000000 1496150 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": 1028207, "vin": [ { "gen": { "height": 1028197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf54b5238ea1828b258dbae490576116ec559abb2b440eeffe4cc0629f80d8a4" } } ], "extra": [ 1, 169, 134, 190, 2, 238, 77, 170, 159, 19, 190, 47, 136, 193, 194, 145, 20, 109, 150, 67, 125, 196, 145, 156, 159, 236, 196, 194, 21, 52, 240, 185, 168, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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