Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d963a1817dbef9cd61827692808a06fc043d21c8054517a2d68b3101cfcac0e

Tx prefix hash: 986135b22afceef306fbcf668ec668e4e59c8551f0eba99790e68bbade21dd3c
Tx public key: df16928eec90274cf55153d16063191f89f35e9c96d2dd22f821a3f9e4f8e0af
Timestamp: 1709432794 Timestamp [UCT]: 2024-03-03 02:26:34 Age [y:d:h:m:s]: 01:073:01:54:21
Block: 969951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313258 RingCT/type: yes/0
Extra: 01df16928eec90274cf55153d16063191f89f35e9c96d2dd22f821a3f9e4f8e0af02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c188cb93efa2a026e727706bdca9e598d7cd0d335849230acbc2cee819d08328 0.600000000000 1429800 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": 969961, "vin": [ { "gen": { "height": 969951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c188cb93efa2a026e727706bdca9e598d7cd0d335849230acbc2cee819d08328" } } ], "extra": [ 1, 223, 22, 146, 142, 236, 144, 39, 76, 245, 81, 83, 209, 96, 99, 25, 31, 137, 243, 94, 156, 150, 210, 221, 34, 248, 33, 163, 249, 228, 248, 224, 175, 2, 17, 0, 0, 0, 5, 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