Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7528d81bd49efefb5ae2135210d5dc215d27a03e0a64da84a941286b6f9e06b

Tx prefix hash: 27f19e2c8c46afb73f8e713b79d540a02ee68c326bc525d1a1ef270ff2dad878
Tx public key: 603a8b630dc1e895a6f932998e57e2a6f25203ccbdd728f9841970522c7f8dc2
Timestamp: 1729236450 Timestamp [UCT]: 2024-10-18 07:27:30 Age [y:d:h:m:s]: 00:020:03:22:31
Block: 1134135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14335 RingCT/type: yes/0
Extra: 01603a8b630dc1e895a6f932998e57e2a6f25203ccbdd728f9841970522c7f8dc20211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13175014aaea5687ea3eab3574a864c3a9166787e9cfee9ab828e7e9ba58da15 0.600000000000 1617390 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": 1134145, "vin": [ { "gen": { "height": 1134135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13175014aaea5687ea3eab3574a864c3a9166787e9cfee9ab828e7e9ba58da15" } } ], "extra": [ 1, 96, 58, 139, 99, 13, 193, 232, 149, 166, 249, 50, 153, 142, 87, 226, 166, 242, 82, 3, 204, 189, 215, 40, 249, 132, 25, 112, 82, 44, 127, 141, 194, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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