Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e03b8025bdc23c680f6226cf186a27fd8d51cb806188d6b3cc1acca27aaca38a

Tx prefix hash: 0a94c0dfb3fdd87d05b6ab46e33145601aec413702e5dcfc8c64c7593621c749
Tx public key: 9c8634cc76ed541398e7e9ec101b3322cad7e66b44ead385d88146a6cde775fb
Timestamp: 1578327052 Timestamp [UCT]: 2020-01-06 16:10:52 Age [y:d:h:m:s]: 04:304:16:20:15
Block: 39807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107164 RingCT/type: yes/0
Extra: 019c8634cc76ed541398e7e9ec101b3322cad7e66b44ead385d88146a6cde775fb02110000000d4943cd9f000000000000000000

1 output(s) for total of 453.005768461000 dcy

stealth address amount amount idx
00: f2be28d0528c26e40f2fd906de1b7ffbd67e452e3a28dbc4d707b48ffa03efdd 453.005768461000 69171 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": 39817, "vin": [ { "gen": { "height": 39807 } } ], "vout": [ { "amount": 453005768461, "target": { "key": "f2be28d0528c26e40f2fd906de1b7ffbd67e452e3a28dbc4d707b48ffa03efdd" } } ], "extra": [ 1, 156, 134, 52, 204, 118, 237, 84, 19, 152, 231, 233, 236, 16, 27, 51, 34, 202, 215, 230, 107, 68, 234, 211, 133, 216, 129, 70, 166, 205, 231, 117, 251, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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