Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0731068c53247b74f63b9741cbf7f83ccf1e4a65ce70878ae09c5c5f94c6456f

Tx prefix hash: 12d4b658b92f416bdc3aa4539b537a7c4c8b6578cbedb447dcf32e1ac95f9505
Tx public key: 0bb9df64190a5216f6faa6f10dbf119ab9e82fa229e82bb4f0a1f44da203636c
Timestamp: 1581949142 Timestamp [UCT]: 2020-02-17 14:19:02 Age [y:d:h:m:s]: 04:310:17:29:12
Block: 66835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114498 RingCT/type: yes/0
Extra: 010bb9df64190a5216f6faa6f10dbf119ab9e82fa229e82bb4f0a1f44da203636c021100000001724f989b000000000000000000

1 output(s) for total of 368.594379653000 dcy

stealth address amount amount idx
00: a8d96f943f87807189b74c68d8cfe9eeb3240af5d167b1dda84382fa67098e72 368.594379653000 123049 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": 66845, "vin": [ { "gen": { "height": 66835 } } ], "vout": [ { "amount": 368594379653, "target": { "key": "a8d96f943f87807189b74c68d8cfe9eeb3240af5d167b1dda84382fa67098e72" } } ], "extra": [ 1, 11, 185, 223, 100, 25, 10, 82, 22, 246, 250, 166, 241, 13, 191, 17, 154, 185, 232, 47, 162, 41, 232, 43, 180, 240, 161, 244, 77, 162, 3, 99, 108, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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