Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43ab3c894096cf44b0e0f17c23fe218298f1df4923aeee40ec3965e4552c3ae5

Tx prefix hash: e5e92d6978842966345ab2dc8f5b38f966cac4d4147c5cbd2d375be953711db6
Tx public key: c9641ee2a55ec63188f8b73189afb3d9ecc6a2741388538cf83e404d71b5b64e
Timestamp: 1629771716 Timestamp [UCT]: 2021-08-24 02:21:56 Age [y:d:h:m:s]: 03:193:23:24:31
Block: 319604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 912747 RingCT/type: yes/0
Extra: 01c9641ee2a55ec63188f8b73189afb3d9ecc6a2741388538cf83e404d71b5b64e02110000001a282c04e2000000000000000000

1 output(s) for total of 53.583030651000 dcy

stealth address amount amount idx
00: dbd26c906d2c60e4c5707a020cf7c5c1fd8f82cb679dd3b1e4dcccdbc25261e5 53.583030651000 664005 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": 319614, "vin": [ { "gen": { "height": 319604 } } ], "vout": [ { "amount": 53583030651, "target": { "key": "dbd26c906d2c60e4c5707a020cf7c5c1fd8f82cb679dd3b1e4dcccdbc25261e5" } } ], "extra": [ 1, 201, 100, 30, 226, 165, 94, 198, 49, 136, 248, 183, 49, 137, 175, 179, 217, 236, 198, 162, 116, 19, 136, 83, 140, 248, 62, 64, 77, 113, 181, 182, 78, 2, 17, 0, 0, 0, 26, 40, 44, 4, 226, 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