Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f6bc40c609a4e4459497c72982a60e1ad68418161b106231d4f61042dd0e2b

Tx prefix hash: 57a721084f5d8c906fb63085760bd4677258a9e0fadf6454d446f44d7248cad7
Tx public key: 3b11e19aae1bfc9c344c72beb6b8ff7e1468e7a87ab01ac0c9cc13349a6b9b5b
Timestamp: 1729115007 Timestamp [UCT]: 2024-10-16 21:43:27 Age [y:d:h:m:s]: 00:038:09:04:42
Block: 1133129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27385 RingCT/type: yes/0
Extra: 013b11e19aae1bfc9c344c72beb6b8ff7e1468e7a87ab01ac0c9cc13349a6b9b5b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f4221533a0388bf32cb6c0857cd10edfb7fdf1436e94fff897efd8b567dca7f 0.600000000000 1616198 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": 1133139, "vin": [ { "gen": { "height": 1133129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f4221533a0388bf32cb6c0857cd10edfb7fdf1436e94fff897efd8b567dca7f" } } ], "extra": [ 1, 59, 17, 225, 154, 174, 27, 252, 156, 52, 76, 114, 190, 182, 184, 255, 126, 20, 104, 231, 168, 122, 176, 26, 192, 201, 204, 19, 52, 154, 107, 155, 91, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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