Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d1dec20ccb72c116417bcb4e9c3aafb0be5d9bc0a34a1f4e69e339340c94607

Tx prefix hash: 63c3b2acdca1812e0a466fdc038c5a9d9432581c1e1637e53704be95dc4cc063
Tx public key: b341e94219998948d999d04d16e031423edfe2ac9446624f8dc2cddbd974b9cc
Timestamp: 1704266951 Timestamp [UCT]: 2024-01-03 07:29:11 Age [y:d:h:m:s]: 01:166:23:14:09
Block: 927111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380362 RingCT/type: yes/0
Extra: 01b341e94219998948d999d04d16e031423edfe2ac9446624f8dc2cddbd974b9cc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0800b0dcb3de69d02b4f260d1ffae508c6af6f5500454e178c215bce8b76e608 0.600000000000 1384915 of 15

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": 927121, "vin": [ { "gen": { "height": 927111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0800b0dcb3de69d02b4f260d1ffae508c6af6f5500454e178c215bce8b76e608" } } ], "extra": [ 1, 179, 65, 233, 66, 25, 153, 137, 72, 217, 153, 208, 77, 22, 224, 49, 66, 62, 223, 226, 172, 148, 70, 98, 79, 141, 194, 205, 219, 217, 116, 185, 204, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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