Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77411c774cd6860d02fb929eec22529197c9894da9ce4662abee245b3b9628c3

Tx prefix hash: 6e80e4d11aecdbc0eb653e81d0609020775c816df0a7b927572ed75a3a15b661
Tx public key: 022ed8cd62344732f2228c6048a7843845f051b5976d61715acdefdb7cd23458
Timestamp: 1699786520 Timestamp [UCT]: 2023-11-12 10:55:20 Age [y:d:h:m:s]: 01:150:12:10:44
Block: 889977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368752 RingCT/type: yes/0
Extra: 01022ed8cd62344732f2228c6048a7843845f051b5976d61715acdefdb7cd23458021100000001679a8a81000000000000000000

1 output(s) for total of 0.690457180000 dcy

stealth address amount amount idx
00: 3b7629a491e081931d19bd9aea82a4b7cb561d5acb12c3638489ee84e2bf13b1 0.690457180000 1345996 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": 889987, "vin": [ { "gen": { "height": 889977 } } ], "vout": [ { "amount": 690457180, "target": { "key": "3b7629a491e081931d19bd9aea82a4b7cb561d5acb12c3638489ee84e2bf13b1" } } ], "extra": [ 1, 2, 46, 216, 205, 98, 52, 71, 50, 242, 34, 140, 96, 72, 167, 132, 56, 69, 240, 81, 181, 151, 109, 97, 113, 90, 205, 239, 219, 124, 210, 52, 88, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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