Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18a3fd05fd02bc686a6625698d13a6c0a18d7ce4240cc3ad904117366f85a9c

Tx prefix hash: bb46710d4a50bf5c94d37ae74ef1e93dd8af1388b111ee72c13a2466f78dd790
Tx public key: 2b88ac22b8385412f4817f8051db3e1e0bcc63b4cb5a17beb1e8ac623822832c
Timestamp: 1697796021 Timestamp [UCT]: 2023-10-20 10:00:21 Age [y:d:h:m:s]: 01:164:15:08:16
Block: 873678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378664 RingCT/type: yes/0
Extra: 012b88ac22b8385412f4817f8051db3e1e0bcc63b4cb5a17beb1e8ac623822832c021100000003faf35c9c000000000000000000

1 output(s) for total of 0.781883641000 dcy

stealth address amount amount idx
00: d9e65a557e4d3a33b3d5d79d01161fc93cf3da672eed2f82212f6a0fdc226d9d 0.781883641000 1328838 of 0

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": 873688, "vin": [ { "gen": { "height": 873678 } } ], "vout": [ { "amount": 781883641, "target": { "key": "d9e65a557e4d3a33b3d5d79d01161fc93cf3da672eed2f82212f6a0fdc226d9d" } } ], "extra": [ 1, 43, 136, 172, 34, 184, 56, 84, 18, 244, 129, 127, 128, 81, 219, 62, 30, 11, 204, 99, 180, 203, 90, 23, 190, 177, 232, 172, 98, 56, 34, 131, 44, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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