Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6917c931b065523de29246ac2a075aa1e3c327b186e189b0ec68edeeb3c4756d

Tx prefix hash: 35f7cd85bcc604e0f654b185149d291203f7fc53a4423afc33a51d44473ba5e9
Tx public key: fff8779c4d23160dfbc39303c075eeb00eea9d8bb7131a7347d8805ce7a7187f
Timestamp: 1713845619 Timestamp [UCT]: 2024-04-23 04:13:39 Age [y:d:h:m:s]: 01:018:09:02:42
Block: 1006534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274083 RingCT/type: yes/0
Extra: 01fff8779c4d23160dfbc39303c075eeb00eea9d8bb7131a7347d8805ce7a7187f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e51e41c3b2e577374f9e3ad31e201ff05d8d9cc7498a8fd88934c757a9f49d51 0.600000000000 1467592 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": 1006544, "vin": [ { "gen": { "height": 1006534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e51e41c3b2e577374f9e3ad31e201ff05d8d9cc7498a8fd88934c757a9f49d51" } } ], "extra": [ 1, 255, 248, 119, 156, 77, 35, 22, 13, 251, 195, 147, 3, 192, 117, 238, 176, 14, 234, 157, 139, 183, 19, 26, 115, 71, 216, 128, 92, 231, 167, 24, 127, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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