Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a653d92360e159d0fdd7e4b53aa84477dd14b9b913e68f90c8358179ef2fa0eb

Tx prefix hash: 3b123a05cc7c7080ee1cbbe313fe82aadfaf8b80a9bdaf2a933b16fd644e759c
Tx public key: 3211fa8d9cbe88afe0aa283839cd90bbec4fb2d40100c4de5fc19f5bc66b30a2
Timestamp: 1706955768 Timestamp [UCT]: 2024-02-03 10:22:48 Age [y:d:h:m:s]: 01:276:19:19:18
Block: 949396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456605 RingCT/type: yes/0
Extra: 013211fa8d9cbe88afe0aa283839cd90bbec4fb2d40100c4de5fc19f5bc66b30a202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e07505640ef132e67ab2c2a44d011dfb19c9a8016245c00b2e220e057679cc00 0.600000000000 1407920 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": 949406, "vin": [ { "gen": { "height": 949396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e07505640ef132e67ab2c2a44d011dfb19c9a8016245c00b2e220e057679cc00" } } ], "extra": [ 1, 50, 17, 250, 141, 156, 190, 136, 175, 224, 170, 40, 56, 57, 205, 144, 187, 236, 79, 178, 212, 1, 0, 196, 222, 95, 193, 159, 91, 198, 107, 48, 162, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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