Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e953a1095fe60884f2815ce9d85418e7a041f8afc7980ce018bab3ccabde4b

Tx prefix hash: bd7d2d6602bee582534c93d761f19f96d96692e389f42a326d78cdb8ffdc62ca
Tx public key: caebf01d8edcebbd6caf609a5cba60267aaea1803fffc5502ec405bf2f365afa
Timestamp: 1705447919 Timestamp [UCT]: 2024-01-16 23:31:59 Age [y:d:h:m:s]: 01:341:03:15:06
Block: 936882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502701 RingCT/type: yes/0
Extra: 01caebf01d8edcebbd6caf609a5cba60267aaea1803fffc5502ec405bf2f365afa02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03c7e882f0b7d0e697b9bd83c8db74e419b772f14ba9c7fddf1f5694cf83f3d0 0.600000000000 1394924 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": 936892, "vin": [ { "gen": { "height": 936882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03c7e882f0b7d0e697b9bd83c8db74e419b772f14ba9c7fddf1f5694cf83f3d0" } } ], "extra": [ 1, 202, 235, 240, 29, 142, 220, 235, 189, 108, 175, 96, 154, 92, 186, 96, 38, 122, 174, 161, 128, 63, 255, 197, 80, 46, 196, 5, 191, 47, 54, 90, 250, 2, 17, 0, 0, 0, 11, 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