Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1221703853083a913115cb5310c0e8d933da5928dbbde2b7958375b38383508

Tx prefix hash: b034dd4c71a6fb419cc617a83b9bea2d02cbc0c901c48840069817676f50b8aa
Tx public key: 5f174394ffc1e50c7f74fd9deda17cdbc3466a000974a39c4cab25395364dad1
Timestamp: 1638044141 Timestamp [UCT]: 2021-11-27 20:15:41 Age [y:d:h:m:s]: 03:107:16:00:36
Block: 383469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 855652 RingCT/type: yes/0
Extra: 015f174394ffc1e50c7f74fd9deda17cdbc3466a000974a39c4cab25395364dad1021100000012d6e4826b000000000000000000

1 output(s) for total of 32.916101519000 dcy

stealth address amount amount idx
00: 89883e5f8f8d3cfebc71fbb2371a2dcd6c57254e94bf7e5d4c1c642230affd0e 32.916101519000 774188 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": 383479, "vin": [ { "gen": { "height": 383469 } } ], "vout": [ { "amount": 32916101519, "target": { "key": "89883e5f8f8d3cfebc71fbb2371a2dcd6c57254e94bf7e5d4c1c642230affd0e" } } ], "extra": [ 1, 95, 23, 67, 148, 255, 193, 229, 12, 127, 116, 253, 157, 237, 161, 124, 219, 195, 70, 106, 0, 9, 116, 163, 156, 76, 171, 37, 57, 83, 100, 218, 209, 2, 17, 0, 0, 0, 18, 214, 228, 130, 107, 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