Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db4e0d10f2148263eeb5c6d8a46baa544a44d8dcab48acce3c4a0f6152777816

Tx prefix hash: 06a36eaad667170702367ac26f8ebb19dfd3f24eb8176634b9ed22d9dc24ba1a
Tx public key: d4baf481e81e72f327f632cf24b84d57edfa52c8431286d5bc766bf4b86d8d4b
Timestamp: 1728766425 Timestamp [UCT]: 2024-10-12 20:53:45 Age [y:d:h:m:s]: 00:172:23:30:47
Block: 1130234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123405 RingCT/type: yes/0
Extra: 01d4baf481e81e72f327f632cf24b84d57edfa52c8431286d5bc766bf4b86d8d4b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55062e7bc3a0aab6d28e94c6094834a836e9fb63a153ba9a7abd2d33ee5bca58 0.600000000000 1613107 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": 1130244, "vin": [ { "gen": { "height": 1130234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55062e7bc3a0aab6d28e94c6094834a836e9fb63a153ba9a7abd2d33ee5bca58" } } ], "extra": [ 1, 212, 186, 244, 129, 232, 30, 114, 243, 39, 246, 50, 207, 36, 184, 77, 87, 237, 250, 82, 200, 67, 18, 134, 213, 188, 118, 107, 244, 184, 109, 141, 75, 2, 17, 0, 0, 0, 7, 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