Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ffcb718f168315717fd92d32d8fe5131024ef7126643d409bc907f84a019a0a

Tx prefix hash: 92a8ac5fd78e2fd4189210572e06d01d3db41a995491410a524a994243106728
Tx public key: b11ec6837cdcf41fe60277b93aff776eba0bf0e028dd1cbd4825e9b7df99c37c
Timestamp: 1719984595 Timestamp [UCT]: 2024-07-03 05:29:55 Age [y:d:h:m:s]: 00:289:12:25:56
Block: 1057422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206882 RingCT/type: yes/0
Extra: 01b11ec6837cdcf41fe60277b93aff776eba0bf0e028dd1cbd4825e9b7df99c37c021100000001341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a6158d040b05f504efa59bba34a757a53a7fe3a312df5e1ef2339f3822c3c1e 0.600000000000 1527857 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": 1057432, "vin": [ { "gen": { "height": 1057422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a6158d040b05f504efa59bba34a757a53a7fe3a312df5e1ef2339f3822c3c1e" } } ], "extra": [ 1, 177, 30, 198, 131, 124, 220, 244, 31, 230, 2, 119, 185, 58, 255, 119, 110, 186, 11, 240, 224, 40, 221, 28, 189, 72, 37, 233, 183, 223, 153, 195, 124, 2, 17, 0, 0, 0, 1, 52, 16, 1, 174, 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