Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81f66878bf6ed225c9d8e6bc2af0169b94d31523cb8ec72a5dba3e53ce2b9b3e

Tx prefix hash: 3fcd626f40ebaad91e72ab7dd8f1cc533b46e9121dbcf1cb170170d4962d61ca
Tx public key: e941ce8d90a0e86a1d72a463a026dd89761268f1ba4e02e415df687b53af25b3
Timestamp: 1697395217 Timestamp [UCT]: 2023-10-15 18:40:17 Age [y:d:h:m:s]: 01:193:10:18:28
Block: 870361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399271 RingCT/type: yes/0
Extra: 01e941ce8d90a0e86a1d72a463a026dd89761268f1ba4e02e415df687b53af25b3021100000007faf35c9c000000000000000000

1 output(s) for total of 0.801923111000 dcy

stealth address amount amount idx
00: 6717f1de5fec79c331f703a912ebcae9908c561952eef1fce6c7bfab9e8fd8d8 0.801923111000 1325240 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": 870371, "vin": [ { "gen": { "height": 870361 } } ], "vout": [ { "amount": 801923111, "target": { "key": "6717f1de5fec79c331f703a912ebcae9908c561952eef1fce6c7bfab9e8fd8d8" } } ], "extra": [ 1, 233, 65, 206, 141, 144, 160, 232, 106, 29, 114, 164, 99, 160, 38, 221, 137, 118, 18, 104, 241, 186, 78, 2, 228, 21, 223, 104, 123, 83, 175, 37, 179, 2, 17, 0, 0, 0, 7, 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