Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69e4b9dc047a0d06df673554611a107bf9c7edb64199392033e85a84a78836b8

Tx prefix hash: bd469a010ae5e3ab5c8c04d967d9946e6e878585c1dcc11db56133bd3ed2dbdf
Tx public key: 301b6dd868e6c42de719acfbe4fde4791f61e98a40e98492ebd3bf6eccc52f43
Timestamp: 1707092746 Timestamp [UCT]: 2024-02-05 00:25:46 Age [y:d:h:m:s]: 01:077:23:24:41
Block: 950536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316790 RingCT/type: yes/0
Extra: 01301b6dd868e6c42de719acfbe4fde4791f61e98a40e98492ebd3bf6eccc52f430211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66d79284723bdb3e478f6e075d3ed82c9115c5e061deee4a804e77ff787b1d3d 0.600000000000 1409172 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": 950546, "vin": [ { "gen": { "height": 950536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66d79284723bdb3e478f6e075d3ed82c9115c5e061deee4a804e77ff787b1d3d" } } ], "extra": [ 1, 48, 27, 109, 216, 104, 230, 196, 45, 231, 25, 172, 251, 228, 253, 228, 121, 31, 97, 233, 138, 64, 233, 132, 146, 235, 211, 191, 110, 204, 197, 47, 67, 2, 17, 0, 0, 0, 3, 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