Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d951b6e80f2ca5bf78da0c9920e39e0932a76efc5f2e464f9fa87eeac627e7f2

Tx prefix hash: 27072e895f2dcfabec0f4b1fdc788d46e056371e436ce1109c53716e4464b1ff
Tx public key: 6f628df21ecd2865a80b61ec058202272c140ca174afb14fd8a4ccc6e0aa2134
Timestamp: 1674902294 Timestamp [UCT]: 2023-01-28 10:38:14 Age [y:d:h:m:s]: 02:027:06:23:23
Block: 684548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541083 RingCT/type: yes/0
Extra: 016f628df21ecd2865a80b61ec058202272c140ca174afb14fd8a4ccc6e0aa21340211000000025029cbac000000000000000000

1 output(s) for total of 3.309849468000 dcy

stealth address amount amount idx
00: 096735bd79d92dd4c054bd4b0a775c7e945eb3beb50d1d11ac6ac171b0477129 3.309849468000 1126799 of 0

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": 684558, "vin": [ { "gen": { "height": 684548 } } ], "vout": [ { "amount": 3309849468, "target": { "key": "096735bd79d92dd4c054bd4b0a775c7e945eb3beb50d1d11ac6ac171b0477129" } } ], "extra": [ 1, 111, 98, 141, 242, 30, 205, 40, 101, 168, 11, 97, 236, 5, 130, 2, 39, 44, 20, 12, 161, 116, 175, 177, 79, 216, 164, 204, 198, 224, 170, 33, 52, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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