Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5612058a5e4cad0708b821ca1757e117f2dd400667d23d9982777fdb829fbdda

Tx prefix hash: 0ba4ae41596844ec5c6d4a7c56f6ce296496fdaefcf4452dc7873d29a313c296
Tx public key: ba89f6c8748bda24c8b373cd2457d908c30b3b62ed1f761c295f3fae2ee0ee3c
Timestamp: 1714813584 Timestamp [UCT]: 2024-05-04 09:06:24 Age [y:d:h:m:s]: 00:332:01:29:22
Block: 1014565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237346 RingCT/type: yes/0
Extra: 01ba89f6c8748bda24c8b373cd2457d908c30b3b62ed1f761c295f3fae2ee0ee3c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3489ead53160402ee39f07e12a32d9016afdf88c35f2ed70bc456dae02996dd0 0.600000000000 1477690 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": 1014575, "vin": [ { "gen": { "height": 1014565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3489ead53160402ee39f07e12a32d9016afdf88c35f2ed70bc456dae02996dd0" } } ], "extra": [ 1, 186, 137, 246, 200, 116, 139, 218, 36, 200, 179, 115, 205, 36, 87, 217, 8, 195, 11, 59, 98, 237, 31, 118, 28, 41, 95, 63, 174, 46, 224, 238, 60, 2, 17, 0, 0, 0, 4, 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