Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e19d5fa327750e6561b981beda52f3e6b9858bee51423b1944cbbeeadf7c613c

Tx prefix hash: 443a795b7606019593455fc14275e63b61db021ff4f1d8a79a87ac668539949e
Tx public key: e0e1bd5ed5f652d0928b10d96a8e2dc2708c9347ab1ac15d6978f780628640ce
Timestamp: 1672438295 Timestamp [UCT]: 2022-12-30 22:11:35 Age [y:d:h:m:s]: 01:337:10:47:45
Block: 664105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502220 RingCT/type: yes/0
Extra: 01e0e1bd5ed5f652d0928b10d96a8e2dc2708c9347ab1ac15d6978f780628640ce021100000001e7ace25d000000000000000000

1 output(s) for total of 3.868516181000 dcy

stealth address amount amount idx
00: 2fa7c12e5d7f640f21d5b5f6d65c37a7b44b130bc6eeae3e67bca60817131e67 3.868516181000 1105076 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": 664115, "vin": [ { "gen": { "height": 664105 } } ], "vout": [ { "amount": 3868516181, "target": { "key": "2fa7c12e5d7f640f21d5b5f6d65c37a7b44b130bc6eeae3e67bca60817131e67" } } ], "extra": [ 1, 224, 225, 189, 94, 213, 246, 82, 208, 146, 139, 16, 217, 106, 142, 45, 194, 112, 140, 147, 71, 171, 26, 193, 93, 105, 120, 247, 128, 98, 134, 64, 206, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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