Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fc7ab4a853bab37983bcfae3f9e172765db28329290e75f60a30d2e7a3c563a

Tx prefix hash: 5afdd58c0d795dbb72d2d6f74806bffe1e87b3951562432b4c6aa2c1c35a9a0c
Tx public key: 051dc4b1502f0bc2149ddfb0e9a024c95145f4d5e1ae3a37ba941fd973255279
Timestamp: 1707508541 Timestamp [UCT]: 2024-02-09 19:55:41 Age [y:d:h:m:s]: 00:335:02:06:21
Block: 953982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239900 RingCT/type: yes/0
Extra: 01051dc4b1502f0bc2149ddfb0e9a024c95145f4d5e1ae3a37ba941fd973255279021100000002ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 334b29505836442e4b0d8dfdc35b2318652ca9c3430537ae716c1afea66e424a 0.600000000000 1413254 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": 953992, "vin": [ { "gen": { "height": 953982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "334b29505836442e4b0d8dfdc35b2318652ca9c3430537ae716c1afea66e424a" } } ], "extra": [ 1, 5, 29, 196, 177, 80, 47, 11, 194, 20, 157, 223, 176, 233, 160, 36, 201, 81, 69, 244, 213, 225, 174, 58, 55, 186, 148, 31, 217, 115, 37, 82, 121, 2, 17, 0, 0, 0, 2, 236, 87, 178, 52, 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