Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b31a53720e2714a77406e0812cdb40b7ad762ae7f4e7ec522835512be6d018b

Tx prefix hash: 32f318b1002d8eb0c20cc053b58a2cf678ef894313c56d9eb7c87f4430f8e1eb
Tx public key: f94b774becf49f44b1e82a4599d8b4c85668d9c6dccaa9e8692194d685e82099
Timestamp: 1734058039 Timestamp [UCT]: 2024-12-13 02:47:19 Age [y:d:h:m:s]: 00:186:22:28:57
Block: 1174014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133305 RingCT/type: yes/0
Extra: 01f94b774becf49f44b1e82a4599d8b4c85668d9c6dccaa9e8692194d685e820990211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e58809f906ff46c9ab78b64ff701e70748590c133f8aeb3e0afe84d0a087150 0.600000000000 1660113 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": 1174024, "vin": [ { "gen": { "height": 1174014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e58809f906ff46c9ab78b64ff701e70748590c133f8aeb3e0afe84d0a087150" } } ], "extra": [ 1, 249, 75, 119, 75, 236, 244, 159, 68, 177, 232, 42, 69, 153, 216, 180, 200, 86, 104, 217, 198, 220, 202, 169, 232, 105, 33, 148, 214, 133, 232, 32, 153, 2, 17, 0, 0, 0, 3, 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