Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60f4357a30cd61234a85cf3284c41c704e0e38e052f2e35f6aa9c93c3a913f34

Tx prefix hash: 5ac76ca07cfa5e40111663ff76d85ea3af1d6b72a35aabae00801064b4514704
Tx public key: 1ac818d2d5fc6042e86be298c4c9ca138b7d00783c0b087f7021ed93d9ee4134
Timestamp: 1731109038 Timestamp [UCT]: 2024-11-08 23:37:18 Age [y:d:h:m:s]: 00:015:05:22:07
Block: 1149571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10887 RingCT/type: yes/0
Extra: 011ac818d2d5fc6042e86be298c4c9ca138b7d00783c0b087f7021ed93d9ee4134021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 282dbfec61bba48d1dbd95986c8794e6b03d88d0368dd9ae4e05cdcf78a92dc0 0.600000000000 1634676 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": 1149581, "vin": [ { "gen": { "height": 1149571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "282dbfec61bba48d1dbd95986c8794e6b03d88d0368dd9ae4e05cdcf78a92dc0" } } ], "extra": [ 1, 26, 200, 24, 210, 213, 252, 96, 66, 232, 107, 226, 152, 196, 201, 202, 19, 139, 125, 0, 120, 60, 11, 8, 127, 112, 33, 237, 147, 217, 238, 65, 52, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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