Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f3f8daa1016884ff3ec8b69a927ebb784dad3b8a2e572ab207f6858c610af94

Tx prefix hash: b50df266d1b388a62487c761cf236c9d958017d4c1c1f9f66cfee1bfefc7369e
Tx public key: 07974de6c8e4e9421f69757588ed5e60548675459eeb0d6daab5c35c638bc515
Timestamp: 1734754975 Timestamp [UCT]: 2024-12-21 04:22:55 Age [y:d:h:m:s]: 00:317:23:35:00
Block: 1179787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224745 RingCT/type: yes/0
Extra: 0107974de6c8e4e9421f69757588ed5e60548675459eeb0d6daab5c35c638bc5150211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3107b372254027262fba330a4b6a3aee9ca49cc1f096f993cb086e64b7207bc 0.600000000000 1666186 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": 1179797, "vin": [ { "gen": { "height": 1179787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3107b372254027262fba330a4b6a3aee9ca49cc1f096f993cb086e64b7207bc" } } ], "extra": [ 1, 7, 151, 77, 230, 200, 228, 233, 66, 31, 105, 117, 117, 136, 237, 94, 96, 84, 134, 117, 69, 158, 235, 13, 109, 170, 181, 195, 92, 99, 139, 197, 21, 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