Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86f4e9618ac79a4e57ac021334c2cb5a68178f49331c16170d7c5cb7d95e0bf4

Tx prefix hash: b66951a46049d1e38055254542684b5ee078b5e6402cb713fa7ed9d2d6f7ad26
Tx public key: ffc4795aa1296d95d3fddb70fc69da22d6e84d5110dc2751322e0282428666e5
Timestamp: 1714176816 Timestamp [UCT]: 2024-04-27 00:13:36 Age [y:d:h:m:s]: 00:344:10:48:23
Block: 1009269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246241 RingCT/type: yes/0
Extra: 01ffc4795aa1296d95d3fddb70fc69da22d6e84d5110dc2751322e0282428666e50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5b085ff32e25e3c3150996691974bf8ef59e84feada9793ae20f0269c717156 0.600000000000 1470893 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": 1009279, "vin": [ { "gen": { "height": 1009269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5b085ff32e25e3c3150996691974bf8ef59e84feada9793ae20f0269c717156" } } ], "extra": [ 1, 255, 196, 121, 90, 161, 41, 109, 149, 211, 253, 219, 112, 252, 105, 218, 34, 214, 232, 77, 81, 16, 220, 39, 81, 50, 46, 2, 130, 66, 134, 102, 229, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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